Prolog thousand database

This file is a preliminary version of a database of applications of Prolog and related languages, containing over 500 entries. It is made available for the benefit of the Prolog community. It may be freely copied, but not published without the explicit permission of the maintainers below.
It does not contain the full addresses of the authors of the software. Anyone who wishes to follow up a reasonable number of entries should send an email message to Al Roth (alroth@cix.clink.co.uk) who will be happy to supply these details. 
If you haven't submitted an entry, a copy of the original submission form is given below.
-------------------------------------------------------------
Entries may be made either by the original authors or (by agreement) those in 
contact with them who have access to the information asked for (which includes 
the size of program and time taken). Entries are not limited to commercial 
programs - shareware and non-distributed and privately used programs are 
perfectly acceptable, but we are not interested in programming exercises. The 
results of research projects may be submitted if they have actually been used 
for their designed end.
An entry only takes a few minutes, so why not do it right away? Pass this file 
on to your friends and get them to enter too!
Send entries to:
	Al Roth, PO Box 137, Blackpool, Lancashire, FY2 0XY, U.K.    
	Email: alroth@cix.compulink.co.uk
	Fax: +44 253 53811 Telephone: +44 253 58081. 
	(Floppy disks for PC or Mac in text form are also welcome, 
		and paper entries may also be sent).
Queries may also be addressed to the people who conceived the project:
	Chris Moss (cdsm@doc.ic.ac.uk)
	Leon Sterling (leon@alpha.ces.cwru.edu)
Sponsored by:  ALP-UK, Dept. Computing, Imperial College, London SW7 2BZ
	Email: alpuk@doc.ic.ac.uk
------------------------------------------------------------
Entry Form and submission details
=================================
Put your details in place of the description below, leaving the field names in 
angle brackets. Do not  use angle brackets elsewhere, but free use of spaces and 
newlines is ok. Several entries may placed after each other in the same file.
<Program>  what it is conventionally called in the documentation
	<Purpose> (up to 20 words)
	<Developers>    people mainly responsible
	<Organization>  directing or sponsoring the work
	<Country> in which developed
	<Domain>  the work area and activity to which this is relevant. 
		Try and be as specific as possible. e.g.: Electronic 
		Design, Financial Analysis, Legal Drafting, Medical  
		Diagnosis. General descriptions such as CAD or Decision 
		Support should be used only if the product is directly 
		useful for several work areas.
	<Contact> Name of someone who can answer questions, with 
	<Address> and<Telephone>     and<Email>   address (or fax number) for the contact (if known)
	<Description>   (up to150 words)
	<Prolog>  Name of interpreter/compiler(s) used
	
	<Platform>      Hardware / operating system(s) (development / delivery)
	<Other Languages>    or systems used, with approximate extent
	<Lines>   Approximate number of lines of Prolog
	<Predicates>    Approximate number of Prolog predicates
	<Development effort> Number of person-months for initial system
	<Maintenance effort> Number of person-months since, including enhancements
	<Current Status>     1=Prototype, 2=Evaluation, 3=Released, 
		4=No longer supported, 5=Dead
	<Use>     1=Personal use, 2=in-House use, 3=Free/public domain, 
		4=Licensed, 5=Sold product 
	<Users>   Approximate number
	<Date deployed> Month/year of inital practical use of program
	<Dated>   date to which this information refers
	<References>    Citations of published or available work, if any 
</Program>     This ends the entry.
------------------------------------------------------------
NOTES LG :
    - all lines are not filled in
    - about 500 entries
    - some special characters : needs unicode parsing
    - exploitation of data base :
        + some cleanup for some special chars
        + results have  been transferred to .json file, with similar structure 
        + field 'year' added as 
                * the exact value of <Date deployed> if available, 
                * otherwise will search the largest year value in other fields, 
                * 1900 if nothing found